Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0429

reference
410-tree-1
name
0429
tree-preservation-order

undefined

410-tpo-1
uprn
address-text
point
POINT (-1.022540 50.890554)
geometry
MULTIPOLYGON (((-1.022413 50.890540,-1.022418 50.890565,-1.022436 50.890588,-1.022464 50.890606,-1.022499 50.890618,-1.022539 50.890622,-1.022579 50.890619,-1.022614 50.890608,-1.022643 50.890590,-1.022662 50.890567,-1.022669 50.890543,-1.022663 50.890517,-1.022645 50.890495,-1.022617 50.890477,-1.022582 50.890465,-1.022542 50.890461,-1.022503 50.890464,-1.022467 50.890475,-1.022438 50.890493,-1.022419 50.890515,-1.022413 50.890540)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL